![]() | ![]() | ![]() | ![]() |
In SAS® Merchandise Allocation, an IPC_CONNECTION_BROKEN and IPC_CORRUPTED_DATA exception might be generated with exception details similar to the following in the log:
ERROR com.sas.retail.merchplan.mecommon.Connection - java.io.IOException: An existing connection was forcibly closed by the remote host at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:197) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) at com.sas.retail.merchplan.mecommon.Connection.receive(Unknown Source) at com.sas.retail.merchplan.mecommon.Header.receive(Unknown Source) at com.sas.retail.merchplan.mecommon.Connection.receive(Unknown Source) at com.sas.retail.merchplan.mecommon.PassivePEInstMon.HandleActiveInstMessage(Unknown Source) at com.sas.retail.merchplan.mecommon.PassivePEInstMon$ActiveInstRunner.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)
This exception is generated when performing different functions in an allocation worksheet such as recalculations, edits, or copying and pasting data. Once the exception is generated, you are forced to close and reopen the worksheet, which results in the loss of data.
There is no workaround for this issue.
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS Merchandise Allocation | Microsoft Windows Server 2008 R2 | 3.5_M1 | 3.5_M1 | 9.4 TS1M2 | 9.4 TS1M2 |
Linux for x64 | 3.5_M1 | 3.5_M1 | 9.4 TS1M2 | 9.4 TS1M2 | ||
64-bit Enabled AIX | 3.5_M1 | 3.5_M1 | 9.4 TS1M2 | 9.4 TS1M2 |